docs: update capacity-planning for block storage#6936
Open
CharlieTLe wants to merge 1 commit intocortexproject:masterfrom
Open
docs: update capacity-planning for block storage#6936CharlieTLe wants to merge 1 commit intocortexproject:masterfrom
CharlieTLe wants to merge 1 commit intocortexproject:masterfrom
Conversation
Update capacity planning guide for blocks storage with detailed parameters and component requirements Signed-off-by: Charlie Le <charlie_le@apple.com>
yeya24
reviewed
Aug 3, 2025
|
|
||
| Some key parameters to consider: | ||
|
|
||
| 1. **Number of active series**: If you have Prometheus already, you can query [`prometheus_tsdb_head_series`](https://prometheus.io/docs/prometheus/latest/querying/functions/#prometheus_tsdb_head_series) to see this number. |
Contributor
There was a problem hiding this comment.
We can keep this but maybe also refer to the Cortex ingester metric as well? A lot of users might using non Prometheus collector such as Otel today.
| Some key parameters to consider: | ||
|
|
||
| 1. **Number of active series**: If you have Prometheus already, you can query [`prometheus_tsdb_head_series`](https://prometheus.io/docs/prometheus/latest/querying/functions/#prometheus_tsdb_head_series) to see this number. | ||
| 2. **Sampling rate**: e.g. a new sample for each series every minute (the default Prometheus [scrape_interval](https://prometheus.io/docs/prometheus/latest/configuration/configuration/)). Multiply this by the number of active series to get the total rate at which samples will arrive at Cortex. |
Contributor
There was a problem hiding this comment.
Can we just say scrape interval? Sampling rate as a term seems mainly for tracing.
| ## Production Recommendations | ||
|
|
||
| 1. **Enable caching**: Configure [index, chunks, and metadata caching](../blocks-storage/production-tips.md#caching) for store-gateways and queriers. | ||
| 2. **Enable bucket index**: Use [bucket index](../blocks-storage/bucket-index.md) to reduce object storage API calls. |
Contributor
There was a problem hiding this comment.
We should mark bucket index as non experimental in Cortex.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does: Updates capacity planning guide for blocks storage with detailed parameters and component requirements
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]